Address issues with VSIX item publishing projects and FUTDC #74470
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Workaround missing dependency publishing feature in the VS SDK.
Introduces the following convention: When a project reference publish outputs (i.e. more than standard build outputs) need to be packaged into a VSIX,
the project should define
VsixItemsOutputGroup
target and include it inProjectRefrence.IncludeOutputGroupsInVSIX
.VsixItemsOutputGroup
target may gather all the publishing items to be packaged into the VSIX usingPublishItemsOutputGroup
target,but should not depend on
Publish
target (i.e. invokingVsixItemsOutputGroup
target should not trigger actual publishing).A custom target run before
CreateVsixContainer
will take care of publishing for allProjectReferences
withVsixItemsOutputGroup
.